[% setvar title Keep C<use less>, but make it work. %]
<div id="archive-notice">
    <h3>This file is part of the Perl 6 Archive</h3>
    <p>To see what is currently happening visit <a href="http://www.perl6.org/">http://www.perl6.org/</a></p>
</div>
<div class='pod'>
<a name='TITLE'></a><h1>TITLE</h1>
<p>Keep <code>use less</code>, but make it work.</p>
<a name='VERSION'></a><h1>VERSION</h1>
<pre>  Maintainer: Simon Cozens &lt;<a href='mailto:simon@brecon.co.uk'>simon@brecon.co.uk</a>&gt;
  Date: 25 Sep 2000
  Mailing List: <a href='mailto:perl6-internals@perl.org'>perl6-internals@perl.org</a>
  Number: 303
  Version: 1
  Status: Developing</pre>
<a name='ABSTRACT'></a><h1>ABSTRACT</h1>
<p><code>use less</code> is the semi-humorous Perl 5 pragma which should give the
interpreter hints as to how to make memory-speed tradeoffs. Make it
actually <b>do</b> something in Perl 6.</p>
<a name='DESCRIPTION'></a><h1>DESCRIPTION</h1>
<p>None.</p>
<a name='IMPLEMENTATION'></a><h1>IMPLEMENTATION</h1>
<p><code>use less</code> should be renamed to <code>use optimize</code> for Perl 6, and
memory-speed tradeoffs should be identified and the appropriate choice
made; this is of especial merit when compiling to standalone executable.
Of course, since we don't know what the memory-speed tradeoffs are going
to be until we start coding, it's a bit hard to give a more detailed
implementation suggestion.</p>
<p><code>optimize</code> was chosen because then more fine-grained optimisations may
be specified: see &quot;Unrolling loops and tail recursion&quot; for some
examples.</p>
<a name='REFERENCES'></a><h1>REFERENCES</h1>
<p>RFC 302: Unrolling loops and tail recursion</p>
</div>
